Record Locking

Deacom locks records from being modified by multiple users, both in the classic and web versions, in the following areas of the system (table name included):

  • Purchase Orders (dttpur)
  • Sales Orders (dttord)
  • Jobs (dtjob) in versions 15.02.036 and below, or Job Lines (dtljob) in versions 15.02.037 and above.
  • Formulation (dmrev)
  • Item Masters (dmprod)
  • QC Results (dtqc3)
  • Bill-to Customers (dmbill)
  • Ship-to Customers (dmship)
  • Physical Inventory Worksheets (dtphys)
  • Temporary Journal Entries (dtjour) (in versions 17.02.018 and above)

A record is locked once a user modifies a form used to edit one of the tables listed above. This record lock is noted in the dtlock table. If another user tries to modify a record that is logged in the dtlock table, a system prompt is displayed to the new user with the user's name who currently has the record locked and the date/time the record was locked. Non-critical record locks can be overridden by users with the proper security ("sales orders -- override modify lock", "purchase orders -- override modify lock", ...), but critical record locks cannot be overridden by anyone. Once the user who has the table locked exits the form, the lock noted in the dtlock table is removed.

Record locks are now invalidated when the user that took them logs out. Specifically, all record locks for a user are removed from the dtlock table once the user logs out of Deacom via File > Exit. If a logged program error occurs while a record lock is in place, it is possible that the record lock will not be removed. To remove a non-critical record lock, a user with the security to override a locked record ("sales orders -- override modify lock", "purchase orders -- override modify lock", ...) should re-save the order and exit Deacom. Or, the user who applied the lock can re-save the record and exit Deacom. Only the user who applied the lock can undo a critical record lock by re-saving the record and exiting Deacom.

Note: (As of version 17.04.008) - A new reserve lock type was introduced when users are reserving inventory against sales orders in the main application. This lock works in connection with the "Allow Multiple Users To Reserve Simultaneously" field in Sales > Options.

  • If this field is not checked, then users will receive the proper lock message depending on their security for "Sales – Override Record Lock". If the user has security to override they should be able to steal the lock like the current editing lock.
  • If this field is checked, the system will allow the user to enter the reserve transaction and place another reserve lock on the sales order for the new user's transaction. A prompt will list all users with a reserve lock.

Critical vs non-critical record locking

Record locks in Deacom can be critical or non-critical. An example of each type is provided below.

A critical lock is if the sales order is in the process of being shipped or if a purchase order is in the process of being received. For example, if a user navigates to Sales > Ship Sales Order, selects a sales order and clicks the "Continue" button they will be presented with the "Lines From Order" form which is the shipping form. At this point no one can touch that order. The same thing would apply in the Purchasing > Receive transaction.

A non-critical lock is if you are editing a sales order or purchase order ( not shipping or receiving) and someone, with the appropriate security setting, comes along and overrides you.

Additional web version specific record locking features

Deacom web versions add the ability to lock job lines when issuing, de-issuing, editing, inputting production, and during the close/relieve process. This prevents other users from trying to modify a job line that another user currently has locked under their user id. The only lock that can be overridden is when the user clicks "Modify", and then another user that has the security to override clicks "Modify" on their side. Web versions also add the ability to lock Sales Orders when issuing and de-issuing.